Empty Test ^^^^^ **Definition:** * Occurs when a test method has no executable statements. Such methods are possibly created for debugging purposes without being deleted or contain commented-out test statements. An empty test method can be considered problematic and more dangerous than not having a test case at all since JUnit will indicate that the test passes even if there are no executable statements present in the method body. As such, developers introducing behavior-breaking changes into production class, will not be notified of the alternated outcomes as JUnit will report the test as passing. **Code Example:** .. code-block:: java public void testCredGetFullSampleV1() throws Throwable{ // ScrapedCredentials credentials = innerCredTest(FULL_SAMPLE_v1); // assertEquals("p4ssw0rd", credentials.pass); // assertEquals("user@example.com",credentials.user); } **References:** .. admonition:: Quality attributes * :octicon:`file-code;1em` - Code Example * :octicon:`comment-discussion;1em` - Cause and Effect * :octicon:`graph;1em` - Frequency * :octicon:`sync;1em` - Refactoring * `A survey on test practitioners' awareness of test smells `_ * `An Exploratory Study on the Refactoring of Unit Test Files in Android Applications `_ :octicon:`comment-discussion;1em` :octicon:`sync;1em` * `Automatic Identification of High-Impact Bug Report by Product and Test Code Quality `_ * `Automatic generation of smell-free unit tests `_ :octicon:`comment-discussion;1em` * `Developers perception on the severity of test smells: an empirical study `_ :octicon:`graph;1em` :octicon:`sync;1em` * `Handling Test Smells in Python: Results from a Mixed-Method Study `_ * `How are test smells treated in the wild? A tale of two empirical studies `_ :octicon:`graph;1em` * `Investigating Severity Thresholds for Test Smells `_ :octicon:`comment-discussion;1em` * `Investigating Test Smells in JavaScript Test Code `_ :octicon:`graph;1em` * `Machine Learning-Based Test Smell Detection `_ * `On the Distribution of "Simple Stupid Bugs" in Unit Test Files: An Exploratory Study `_ * `On the diffusion of test smells and their relationship with test code quality of Java projects `_ :octicon:`graph;1em` * `On the distribution of test smells in open source Android applications: an exploratory study `_ :octicon:`file-code;1em` :octicon:`graph;1em` * `On the influence of Test Smells on Test Coverage `_ * `On the test smells detection: an empirical study on the jnose test accuracy `_ :octicon:`graph;1em` * `On the use of test smells for prediction of flaky tests `_ :octicon:`comment-discussion;1em` :octicon:`graph;1em` * `PyNose: A Test Smell Detector For Python `_ :octicon:`comment-discussion;1em` :octicon:`graph;1em` * `Software Unit Test Smells `_ :octicon:`file-code;1em` * `Test Smell Detection Tools: A Systematic Mapping Study `_ * `TestQ: Exploring Structural and Maintenance Characteristics of Unit Test Suites `_ * `The secret life of test smells-an empirical study on test smell evolution and maintenance `_ :octicon:`graph;1em` * `Understanding Testability and Test Smells `_ * `What the Smell? An Empirical Investigation on the Distribution and Severity of Test Smells in Open Source Android Applications `_ :octicon:`file-code;1em` :octicon:`graph;1em` * `tsDetect: an open source test smells detection tool `_